Skip to content

Conversation

@khoa-nguyen-18
Copy link
Contributor

  • Add depend on BOOTLOADER_MCUBOOT for SOC_RA_ENABLE_START_SECOND_CORE config
  • Add support MCUBoot for ek_ra8p1 and mck_ra8t2
  • Remove storage_partition definition for Renesas ek_ra8p1, mck_ra8t2 in the test flash/common

@github-actions
Copy link

github-actions bot commented Oct 18, 2025

The following west manifest projects have changed revision in this Pull Request:

Name Old Revision New Revision Diff
hal_renesas zephyrproject-rtos/hal_renesas@f6950ff zephyrproject-rtos/hal_renesas@fbe4b81 (main) zephyrproject-rtos/[email protected]

All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

Copy link
Contributor

@JarmouniA JarmouniA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add info about MCUboot usage to the board doc? Also, add Kconfig.sysbuild to board folder with the following

choice BOOTLOADER
	default BOOTLOADER_MCUBOOT
endchoice

@khoa-nguyen-18 khoa-nguyen-18 force-pushed the support_renesas_ra8x2_mcuboot branch from ed85ac9 to bb5316e Compare October 22, 2025 08:11
@khoa-nguyen-18
Copy link
Contributor Author

Can you add info about MCUboot usage to the board doc? Also, add Kconfig.sysbuild to board folder with the following

choice BOOTLOADER
	default BOOTLOADER_MCUBOOT
endchoice

Many thanks for your suggestion and the reference. I’ve added the board documentation for MCUboot. However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot. Instead, we guide users to build with the additional configuration option -DSB_CONFIG_BOOTLOADER_MCUBOOT=y.

thenguyenyf
thenguyenyf previously approved these changes Oct 22, 2025
Copy link
Contributor

@thenguyenyf thenguyenyf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Will revisit after manifest is merged

Copy link
Contributor

@JarmouniA JarmouniA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You still need to add Kconfig.sysbuild file. (Non-blocking)
Apply remarks to both boards.

@JarmouniA
Copy link
Contributor

However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot

Those should be the exception, not the general default. Also, you can create a dedicated board variant for those.

@duynguyenxa
Copy link
Member

Can you add info about MCUboot usage to the board doc? Also, add Kconfig.sysbuild to board folder with the following

choice BOOTLOADER
	default BOOTLOADER_MCUBOOT
endchoice

Many thanks for your suggestion and the reference. I’ve added the board documentation for MCUboot. However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot. Instead, we guide users to build with the additional configuration option -DSB_CONFIG_BOOTLOADER_MCUBOOT=y.

However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot

Those should be the exception, not the general default. Also, you can create a dedicated board variant for those.

Hi @nordicjm, @kartben — could we get your thoughts on this?
Should there be a Kconfig.sysbuild default here for MCUboot for the board, or should we leave it out to keep sysbuild generic for both MCUboot and non-MCUboot applications?

@nordicjm
Copy link
Contributor

Can you add info about MCUboot usage to the board doc? Also, add Kconfig.sysbuild to board folder with the following

choice BOOTLOADER
	default BOOTLOADER_MCUBOOT
endchoice

Many thanks for your suggestion and the reference. I’ve added the board documentation for MCUboot. However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot. Instead, we guide users to build with the additional configuration option -DSB_CONFIG_BOOTLOADER_MCUBOOT=y.

However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot

Those should be the exception, not the general default. Also, you can create a dedicated board variant for those.

Hi @nordicjm, @kartben — could we get your thoughts on this? Should there be a Kconfig.sysbuild default here for MCUboot for the board, or should we leave it out to keep sysbuild generic for both MCUboot and non-MCUboot applications?

MCUboot is optional. You can build an application for the board without MCUboot and it builds, flashes and runs fine right? So having MCUboot disabled by default is perfectly fine

west flash -r jlink
MCUboot bootloader
Copy link
Contributor

@nordicjm nordicjm Oct 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this information applies to any board and it seems like good information to have but to have it globally rather than multiple times in different boards - which also means it's easier to maintain updating once then X times in boards - thoughts @kartben ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 -- would suggest adding an rst "snippet" boards/common/doc and the .. literalinclude it wherever needed

Update hal_renesas revision to get MCUBoot support

Signed-off-by: Khoa Nguyen <[email protected]>
Add support MCUBoot for ek_ra8p1 and mck_ra8t2

Signed-off-by: Khoa Nguyen <[email protected]>
Remove storage_partition definition for Renesas ek_ra8p1, mck_ra8t2

Signed-off-by: Khoa Nguyen <[email protected]>
@khoa-nguyen-18 khoa-nguyen-18 force-pushed the support_renesas_ra8x2_mcuboot branch from bb5316e to 82c35a5 Compare October 23, 2025 08:04
@github-actions github-actions bot removed the DNM (manifest) This PR should not be merged (controlled by action-manifest) label Oct 23, 2025
@khoa-nguyen-18
Copy link
Contributor Author

  • Rebase main to solve conflicts
  • Update hal_renesas revision since the HAL PR has been merged
  • Update typos and add missing MCUboot information in the board documentation based on feedback comments

@sonarqubecloud
Copy link

@JarmouniA JarmouniA dismissed their stale review October 23, 2025 08:22

addressed

Copy link
Contributor

@thaoluonguw thaoluonguw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you.

@kartben kartben merged commit e5e1edd into zephyrproject-rtos:main Oct 23, 2025
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Boards/SoCs area: Flash area: Tests Issues related to a particular existing or missing test manifest manifest-hal_renesas platform: Renesas RA Renesas Electronics Corporation, RA platform: Renesas Renesas

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants